feat: set token for deployment #174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mirko Mollik <[email protected]>
cre8
requested review from
lukasjhan,
zustkeeper and
berendsliedrecht
as code owners
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #174 +/- ##
=======================================
Coverage 98.03% 98.03%
=======================================
Files 23 23
Lines 2082 2082
Branches 307 307
=======================================
Hits 2041 2041
Misses 41 41 ☔ View full report in Codecov by Sentry. |
lukasjhan
approved these changes
Mar 12, 2024
|
LGTM :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The release workflow will update the code by writing a new version number to the files. But since we have a protection rule on the main branch, we can not push directly. So the solution is to use a personal github token where the user is authorised to bypass the call.
In the future it would be better to use an app for this, see this discussion.
https://github.com/orgs/community/discussions/13836